Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CORE-16383 Recurring merge from main #1310

Merged

Conversation

ac101m
Copy link
Contributor

@ac101m ac101m commented Oct 20, 2023

Changes

  • Bump API version to 22
  • Merge changes from release/os/5.1

jennyang-r3 and others added 30 commits September 15, 2023 11:56
This PR indexes consumed field of utxo_visible_transaction_state.
This is to improve performance of UtxoPersistenceService.findUnconsumedVisibleStatesByType query so that other tables are pre-sorted by consumed timestamp and query performance improvement.
created index for type of utxo_transaction_output in order to improve performance of findUnconsumedStatesByType query
* Introduces table in vnode-vault schema which holds executed persistence requests (ids) from `PersistenceService`, to be used for deduplicating them
… table (#1257)

Resiliency test run failed caused by exception messages found in db worker logs. The exception messages suggested that the previous length of 255 was too short for the reason column.
Introduce boot config keys for booting the state manager.
- Also fix a config path and some state manager property keys.
* Introduces the api bits needed to introduce the housekeeping functionality for idempotency id table (deduplication table):

  * Adds a timestamp column to hold when a request id was inserted so we can delete old ones
  * Adds a dedicated topic to call the housekeeping functionality through the `Scheduler`
…s used to forcibly remove an existing claim and releasing any claimed tokens back to the cache. This event is generated by the postprocessing stage of the flow event pipeline when a flow completes or fails. (#1258)
Adds counterparty info request and response events, and removes unneeded flow events and states.

The session changes introduced in 5.1 mean that it is possible to request counterparty information before the counterparty is aware the flow exists and has started its initiated flow. This change allows the act of requesting counterparty information to start the initiated flow if required.

---------

Co-authored-by: James Higgs <[email protected]>
…s to support automatic cleanup of orphaned claims. (#1259)
Added a new Token observer interface called `UtxoTokenTransactionStateObserver`.
Deprecated the existing Token observer interface `UtxoLedgerTokenStateObserver`.
Added the token observer context `TokenStateObserverContext`.
Bumped the api version number.
Introducing `FindUnconsumedStatesByExactType` API that will find unconsumed states excluding its subclass states
In CORE-15179 , the db table `config` was updated without following the best practices that have been suggested. This commit moves the code responsible for updating the `config` table to the correct file.
This change adds a reason that is communicated back to the user for declined registrations. It also adjusts the schema of the message that communicates the status back to the member to incorporate this reason.
* Change schema according to the process in the documentation and rollback previous change
…p Avro records (#1265)

Introduces new topics for scheduled cleanup in the flow mapper, and updates the execute cleanup record.

Two new topics are introduced. One is used for publishing scheduled task triggers to the flow mapper. The other is used to publish execute cleanup events to.

Additionally, the execute cleanup Avro record has been updated to allow multiple state IDs to be provided. This allows cleanups to be performed in batches if required.
)

Create new topic for flow processor scheduled tasks.
…ory can be tracked (#1269)

This change adds a command history to the registration state so that registration handlers can take appropriate action based on the previously completed stages. The main use case for this at the moment is to handle replays at the p2p level which cause repeat processing of registration commands. Using the previously processed command list, we can determine in a command processor whether a stage has already been processed successfully or not.
…eduled task name (#1273)

Adds a new schema for scheduled task topics and names for the flow mapper.

These are required to support flow mapper cleanup.
…1263)

This adds an optional forceUpgrade field to the VirtualNodeUpgradeRequest schema which defaults to false.
…e `utxo_transaction_output` (#1275)

The token selection feature uses db queries frequently. Indexing the columns that are used by those queries will improve performance. This commit indexes the columns `token_type`, `token_issuer_hash`, `token_symbol`, and `token_notary_x500_name` from table `utxo_transaction_output`.
…and their status (#1238)

Adding a new request to the UTXO ledger layer to fetch transaction alongside with their status.

This is needed when doing a back-chain resolution. We don't want to fetch transactions that are already present in our database. We just want to fetch their IDs though, no need to deserialise the whole object.
vkolomeyko and others added 10 commits October 6, 2023 13:37
This PR contains the AGREED suggestions from this page: https://r3-cev.atlassian.net/wiki/spaces/CB/pages/4578214028/UTXO+Ledger+Data+Model+Simplifications#Remove-created-field-from-utxo_transaction_component-table-Agreed.

These are:

- Merge utxo_transaction_status table into utxo_transaction (then delete the utxo_transaction_status table) and rename utxo_transaction_output table to utxo_visible_transaction_output
- Merge utxo_visible_transaction_state table into utxo_transaction_output (then delete the utxo_visible_transaction_state table)
- Removal of utxo_transaction_sources table
- Removal of utxo_transaction_cpk and utxo_cpk tables
- Remove created field from utxo_transaction_component table
…42503, part 2 (#1283)

Ensure that even the plugins will be using most up-to-date version.
Promote State Manager configuration to its own section and remove it
from under the Messaging configuration.
Adding a config key for the worker service endpoints to the API package
Claimed tokens are now managed differently which makes the method irrelevant. From release 5.1, nothing will happen if the method is called.
…ver-definitions-same-host-port

DOC-5944 Allow server definitions in Gateway config with same host/port but different path
@ac101m ac101m requested review from a team as code owners October 20, 2023 15:59
@corda-jenkins-ci02
Copy link
Contributor

Jenkins build for PR 1310 build 1

Build Successful:
Jar artifact version produced by this PR: 5.1.0-INTEROP.22-alpha-1697817611544

Copy link
Collaborator

@wzur-r3 wzur-r3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ac101m ac101m merged commit af98814 into release/interop/syntax Oct 23, 2023
1 check passed
@ac101m ac101m deleted the alex/CORE-16383-recurring-merge-from-main branch October 23, 2023 09:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.